New Features for Prizm Content Connect v10.5:
Viewer
- With this release of PCC we are introducing a significant change to the way your application will interact with the PCC conversion services: The Prizm Application Service (PAS) is a service that runs independently of the PCC conversion services and will remove much of the burden of communicating with those services from your code. The PAS is a direct replacement for the existing web tier samples we have been providing, and as a result the web tier samples have become much smaller and easier to understand. It’s also worth noting that your web server can be configured in a way that eliminates the need for these web tier samples altogether. To migrate from the v10.4 (and earlier) web tier, see the topic: Working with Prizm Application Services (PAS) section for details.
- Annotations can now be "burned" into a document the same way that redactions have always been supported. As a result, we have simplified the redaction toolbar, as many of the redaction tools were identical to annotation tools.
- We’ve expanded the set of configuration options for the eSignature modules to allow configuring everything that the full viewer supports.
- We’ve added APIs that allow setting the color of a hyperlink annotation.
- A new Strikethrough annotation type has been added, which allows highlighting text and applying a strikethrough mark over it.
- Rectangle redactions now have user-configurable fill color, line color, and text color.
- Fixed search terms can now be passed into the viewer. These search items will always remain highlighted, and cannot be turned off by the user, even if they initiate other searches.
- We’ve added events to all marks that fire when the end user mouses into, out of, or hovers over the mark’s bounding box.
Imaging Services
- With this release of PCC we optimized SVG payload to improve the HTML5 viewing experience by adding the following features:
- Introduced polyline simplification algorithm (with configurable tolerance) to reduce the number of vertexes in the rendered polylines while maintaining good quality. This significantly minimizes the payload and addresses issues with loading very large CAD files representing maps.
- Enabled conversion of absolute polyline coordinates to relative coordinates, and rounding of polyline coordinates to minimize the payload for viewing CAD files.
- Reduced SVG Payload and improved responsiveness of the HTML5 viewer by introducing and applying the Unicode font replacement method when loading and viewing PDF files.
- Introduced downscaling of all embedded raster images exceeding the configurable size to avoid out-of-memory errors causing a "document not found" error when loading PDF documents with such embedded images.
- We significantly upgraded our Office conversion engine to benefit from the following conversion and rendering fidelity improvements for Office documents:
- Text formatting enhancements for Word documents.
- Improvements in table management to address rendering and positioning inaccuracy with normal and floating tables within Word documents.
- More accurate rendering of check boxes and bullets addressing incorrect background and wrong positioning.
- Better positioning of automatic numbering items for endnotes and footnotes within Word documents.
- More accurate rendering of RTF content.
- Improved rendering of EMF charts within PowerPoint documents.
- Excel rendering improvements in formula engine and conditional formatting.
- Improved rendering of plain text documents containing multiple languages saved with UTF-8 encoding.
- Improved Office conversion error handling and error logging.
- Content Conversion Service has been enhanced with the ability to specify text header and footer to be appended to each page of a document. This feature does not modify the original page content, but expands the overall page dimensions to allow space for the additional header and footer content. This feature allows inserting the current page number and total page count into header and footer text.
- We have made several improvements to the Prizm Licensing Utility messaging, including:
- Better message describing the cause of a failure when a PCC user attempting to install an "annual" node-locked license forgets to specify an access key.
- Message describing the cause of a failure due to invalid licensing configuration file provided by a PCC user attempting to install a license.
- Message describing the cause of a failure due to the access key not matching the provided licensing configuration file when attempting to install a license.
- Message describing the cause of a failure due to exhausted pool of licenses when attempting to install a license.
- Message describing the cause of a failure due to the expired "annual" node-locked license.
- More accurate error reporting when running Prizm Licensing Utility in console mode.
- All PCC options can now be managed through a single Central Configuration File. Please see the topics: Configuration Options > Getting Started with PCC > Configuration Options > Central Configuration and Getting Started with PCC > Configuration Options > Upgrading to Central Configuration in the documentation. Note that the new Central Configuration file is enabled by default in PCC v10.5.
- All PCC Service Caching directories are now kept under a single cache directory under the Prizm install directory on Windows. This can easily be changed using the Central Configuration.
- All PCC Services Logs are now written to a single location on Windows in the Prizm install directory. You can redirect to another directory by using the Central Configuration file.
- The Prizm PCCIS Service is now deployed as a Self-Hosted Solution. Backend Services no longer rely on IIS on Windows or nGinX on Linux Platforms.
- Improvements have been made to the PCC Admin Pages to show the Services starting and stopping in closer to real time.